Thank you so much! Fixed both issues, all CI checks are green now.

Thank you so much for review.
Just out of curiosity, are these changes really break compatibility (and thus require AOT_CURRENT_VERSION bump)? I doubted a bit for two reasons:

1. here are some static asserts that check offsets of some fields in AOTModuleInstanceExtra. When I started to work on this patch I thought that "preserving these offsets is all what required for binary compatibility. If these assertions did not fire, then version bump is not necessary". May be that assumption was wrong, though.
2. One recent PR also changed layout of AOTModuleInstanceExtra, but it did not change AOT_CURRENT_VERSION.

Of course, you, as code owner, know better all nuances. I just write to ensure that we'll not force our users re-compile all their AOT programs without need.

The basic relationship is that WASMModuleInstanceExtraCommon common is a field within AOTModuleInstanceExtra. Subsequent fields, such as functions, will have their offsetof values changed. For protection, we tend to bump AOT_VER to let the AOT loader be aware of that.

PR#4400 was likely overlooked. Currently, the entire review system relies on manual review. Perhaps we could consider introducing other tools to assist.